Repository navigation
test(snapshot): verify compatibility with published 1.0.1 snapshots - #43
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Snapshots written by an older release were covered only by tests that generated data at runtime. A coordinated writer/reader change could therefore pass those tests while breaking saved snapshots.
Add a 1,465-byte fixture written by the published
webgpu-search@1.0.1package, with npm provenance, a SHA-256 checksum, fixed input documents, and nine frozen query expectations. Extend the existing snapshot suite to restore those bytes and check document contents, IDs, ordering, scores, and matched fields. CI already runs the suite. Document fixture preservation and record the coverage in the improvement plan; include a patch changeset.Validation: shader checks, typecheck, build, mock tests, and snapshot tests passed. An independent subagent reproduced identical fixture bytes and query expectations using the released package. A negative control changing a frozen expected score failed in the new historical compatibility check. No runtime library code changed.